Method and system for categorizing items automatically

ABSTRACT

A method and system to automatically categorize a merchant listing in an electronic marketplace are provided. The method includes parsing the category information submitted by a seller to derive a first category identifier. A first search is performed to locate the first category identifier in a first database containing a listing of category identifiers. If no match is found, the first category identifier is identified as expired or invalid. A second search is performed on a second database that includes mapping information of an expired category identifier to a new category identifier. If a match is found, the first category identifier is assigned as the new category identifier, thereby enabling the listing to be listed in the updated category automatically.

FIELD OF THE INVENTION

An embodiment of the present invention relates generally to the field ofonline commerce and more particularly, to a method and a system forcategorizing merchant items in an electronic marketplace, e.g., onlinetrading environment, online shopping site, online auctioning site oronline person-to-person trading site.

BACKGROUND OF THE INVENTION

The Internet and the World Wide Web (“Web”) have changed the landscapeof information delivery and affected numerous aspects of life, includingcommerce and entertainment. One area that has benefited from thistechnology development is the ability of individuals to buy and sellitems within an electronic marketplace.

Many service providers operate auctions and other selling mechanisms onservers connected to the users over one or more networks, typicallyincluding the Internet. The users selling items over these networks varyfrom single users to large corporations, such as Walt Disney Corporationand International Business Machines Corporation. Some users retail theirproducts and services not only through their own electronic marketplacebut also by leveraging third-party electronic marketplaces, such as anauction site.

To enhance the buying and selling experience in the electronicmarketplace, a service provider of such a marketplace may provide manyapplications to facilitate the ease of doing business in themarketplace. One such application may be a category listing applicationthat allows the sellers to conveniently classify their products andservices in a specific location of the marketplace. This classificationin turn facilitates buyers searching for specific goods or services.Examples of the categories available in a marketplace include books,coins, music, home and garden, toys and hobbies, tickets and consumerelectronics.

However, it is challenging for a user to individually categorize a widerange of merchandise in large quantity. For example, Walt DisneyCorporation retails toys, apparels, collectables, theme park tickets andvacation services, where each of these items are listed in differentcategories.

In addition, due to business needs, the service provider of themarketplace may need to make changes to the categories. For example, theservice provider may merge one category with another, add a newcategory, rename an existing category or delete a category. The userneeds to be constantly informed of the changes in order to list an itemin the right category.

SUMMARY OF THE INVENTION

According to one aspect of the invention, there is provided a method tocategorize a merchant listing automatically. In one embodiment, thismethod includes identifying a first category identifier of the merchantlisting; performing a first search to compare the first categoryidentifier with a plurality of category identifiers in a first database;performing a second search to compare the first category identifier witha plurality of category relationships in a second database in responseto no match being found in the first search; providing a second categoryidentifier of the merchant in response to a match being found in thesecond search; and assigning the second category identifier to the firstcategory identifier.

Other features of the present invention will be apparent from theaccompanying drawings and from the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 is a network diagram illustrating a system, according to anexemplary embodiment of the present invention, to categorize an item inan electronic marketplace.

FIG. 2 is a block diagram illustrating multiple marketplace and paymentapplications that, in one exemplary embodiment of the present invention,are provided as part of the electronic marketplace.

FIG. 3 is a network diagram illustrating a category system, according toan exemplary embodiment of the present invention.

FIG. 4 is an interactive flow chart illustrating a method, according toone exemplary embodiment of the present invention, to categorize an itemautomatically.

FIG. 5 is a block diagram representing data information in the databasesof the category system, according to one exemplary embodiment of thepresent invention.

FIG. 6 is a diagrammatic representation of a machine within which a setof instructions, for causing the machine to perform any one of methodsdescribed herein, may be executed.

DETAILED DESCRIPTION

A method and system to categorize an item in an electronic market placeare described. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the present invention. It will be evident,however, to one skilled in the art that the present invention may bepracticed without these specific details.

Platform Architecture

FIG. 1 is a network diagram depicting a system 10, according to oneexemplary embodiment of the present invention, having a client-serverarchitecture. A commerce platform, in the exemplary form of anetwork-based marketplace 12, provides server-side functionality, via anetwork 14 (e.g., the Internet) to one or more clients. FIG. 1illustrates, for example, a web client 16 (e.g., a browser, such as theInternet Explorer browser developed by Microsoft Corporation of Redmond,Wash. State), and a programmatic client 18 executing on respectiveclient machines 20 and 22.

Turning specifically to the network-based marketplace 12, an ApplicationProgram Interface (API) server 24 and a web server 26 are coupled to,and provide programmatic and web interfaces respectively to, one or moreapplication servers 28. The application servers 28 host one or moremarketplace applications 30 and payment applications 32. The applicationservers 28 are coupled to one or more databases servers 34 thatfacilitate access to one or more databases 36.

The marketplace applications 30 provide a number of marketplacefunctions and services to users that access the marketplace 12. Thepayment applications 32 likewise provide a number of payment servicesand functions to users. In one embodiment, the payment applications 30may allow users to quantify for, and accumulate, value (e.g., in acommercial currency, such as the U.S. dollar, or a proprietary currency,such as “points”) in accounts, and then later to redeem the accumulatedvalue for products (e.g., goods or services) that are made available viathe marketplace applications 30. While the marketplace and paymentapplications 30 and 32 are shown in FIG. 1 to both form part of thenetwork-based marketplace 12, it will be appreciated that, inalternative embodiments of the present invention, the paymentapplications 32 may form part of a payment service that is separate anddistinct from the marketplace 12.

Further, while the system 10 shown in FIG. 1 employs a client-serverarchitecture, the present invention is of course not limited to such anarchitecture, and could equally well find application in a distributed,or peer-to-peer, architecture system. The various marketplace andpayment applications 30 and 32 could also be implemented as standalonesoftware programs, which do not necessarily have networkingcapabilities.

The web client 16, it will be appreciated, accesses the variousmarketplace and payment applications 30 and 32 via the web interfacesupported by the web server 26. Similarly, the programmatic client 18accesses the various services and functions provided by the marketplaceand payment applications 30 and 32 via the programmatic interfaceprovided by the API server 24. The programmatic client 18 may, forexample, be a seller application (e.g., the TURBOLISTER applicationdeveloped by eBay Inc., of San Jose, Calif.) to enable sellers to authorand manage listings on the marketplace 12 in an off-line manner, and toperform batch-mode communications between the programmatic client 18 andthe network-based marketplace 12.

FIG. 1 also illustrates a third party application 38, executing on athird party server machine 40, as having programmatic access to thenetwork-based marketplace 12 via the programmatic interface provided bythe API server 24. For example, the third party application 38 may,utilizing information retrieved from the network-based marketplace 12,support one or more features or functions on a website hosted by thethird party. The third party website may, for example, provide one ormore promotional, marketplace or payment functions that are supported bythe relevant applications of the network-based marketplace 12.

Marketplace Applications

FIG. 2 is a block diagram illustrating multiple marketplace and paymentapplications 30 that, in one exemplary embodiment of the presentinvention, are provided as part of the network-based marketplace 12. Themarketplace 12 may provide a number of listing and price-settingmechanisms whereby a seller may list goods or services for sale, a buyercan express interest in or indicate a desire to purchase such goods orservices, and a price can be set for a transaction pertaining to thegoods or services. To this end, the marketplace applications 30 areshown to include one or more auction applications 44 which supportauction-format listing and price setting mechanisms (e.g., English,Dutch, Vickrey, Chinese, Double, Reverse auctions etc.). The variousauction applications 44 may also provide a number of features in supportof such auction-format listings, such as a reserve price feature wherebya seller may specify a reserve price in connection with a listing and aproxy-bidding feature whereby a bidder may invoke automated proxybidding.

A number of fixed-price applications 46 support fixed-price listingformats (e.g., the traditional classified advertisement-type listing ora catalogue listing) and buyout-type listings. Specifically, buyout-typelistings (e.g., including the BUY-IT-NOW (BIN) technology developed byeBay Inc., of San Jose, Calif.) may be offered in conjunction with anauction-format listing, and allow a buyer to purchase goods or services,which are also being offered for sale via an auction, for a fixed-pricethat is typically higher than the starting price of the auction.

Store applications 48 allow sellers to group their listings within a“virtual” store, which may be branded and otherwise personalized by andfor the sellers. Such a virtual store may also offer promotions,incentives and features that are specific and personalized to a relevantseller.

Reputation applications 50 allow parties that transact utilizing thenetwork-based marketplace 12 to establish, build and maintainreputations, which may be made available and published to potentialtrading partners. Consider that where, for example, the network-basedmarketplace 12 supports person-to-person trading, users may have nohistory or other reference information whereby the trustworthiness andcredibility of potential trading partners may be assessed. Thereputation applications 50 allow a user, for example through feedbackprovided by other transaction partners, to establish a reputation withinthe network-based marketplace 12 over time. Other potential tradingpartners may then reference such a reputation for the purposes ofassessing credibility and trustworthiness.

Personalization applications 52 allow users of the marketplace 12 topersonalize various aspects of their interactions with the marketplace12. For example a user may, utilizing an appropriate personalizationapplication 52, create a personalized reference page at whichinformation regarding transactions to which the user is (or has been) aparty may be viewed. Further, a personalization application 52 mayenable a user to personalize listings and other aspects of theirinteractions with the marketplace 12 and other parties.

In one embodiment, the network-based marketplace 12 may support a numberof marketplaces that are customized, for example, for specificgeographic regions. A version of the marketplace 12 may be customizedfor the United Kingdom, whereas another version of the marketplace 12may be customized for the United States. Each of these versions mayoperate as an independent marketplace, or may be customized (orinternationalized) presentations of a common underlying marketplace.

Navigation of the network based-marketplace 12 may be facilitated by oneor more navigation applications 56. For example, a search applicationenables key word searches of listings published via the marketplace 12.A browser application allows users to browse various category,catalogue, or inventory data structures according to which listings maybe classified within the marketplace 12. Various other navigationapplications may be provided to supplement the search and browsingapplications.

In order to make listings, available via the network-based marketplace12, as visually informing and attractive as possible, the marketplaceapplications 30 may include one or more imaging applications 58 whichusers may upload images for inclusion within listings. An imagingapplication 58 also operates to incorporate images within viewedlistings. The imaging applications 58 may also support one or morepromotional features, such as image galleries that are presented topotential buyers. For example, sellers may pay an additional fee to havean image included within a gallery of images for promoted items.

Listing creation applications 60 allow sellers to author convenientlylistings pertaining to goods or services that they wish to transact viathe marketplace 12, and listing management applications 62 allow sellersto manage such listings. Specifically, where a particular seller hasauthored and/or published a large number of listings, the management ofsuch listings may present a challenge. The listing managementapplications 62 provide a number of features (e.g., auto-relisting,inventory level monitors, etc.) to assist the seller in managing suchlistings. One or more post-listing management applications 64 alsoassist sellers with a number of activities that typically occurpost-listing. For example, upon completion of an auction facilitated byone or more auction applications 44, a seller may wish to leave feedbackregarding a particular buyer. To this end, a post-listing managementapplication 64 may provide an interface to one or more reputationapplications 50, so as to allow the seller to provide feedbackconveniently regarding multiple buyers to the reputation applications50.

Dispute resolution applications 66 provide mechanisms whereby disputesarising between transacting parties may be resolved. For example, thedispute resolution applications 66 may provide guided procedures wherebythe parties are guided through a number of steps in an attempt to settlea dispute. In the event that the dispute cannot be settled via theguided procedures, the dispute may be escalated to a third partymediator or arbitrator.

A number of fraud prevention applications 68 implement various frauddetection and prevention mechanisms to reduce the occurrence of fraudwithin the marketplace 12.

Messaging applications 70 are responsible for the generation anddelivery of messages to users of the network-based marketplace 12, suchmessages for example advising users regarding the status of listings atthe marketplace 12 (e.g., providing “outbid” notices to bidders duringan auction process or to provide promotional and merchandisinginformation to users).

Merchandising applications 72 support various merchandising functionsthat are made available to sellers to enable sellers to increase salesvia the marketplace 12. The merchandising applications 80 also operatethe various merchandising features that may be invoked by sellers, andmay monitor and track the success of merchandising strategies employedby sellers.

The network-based marketplace 12 itself, or one or more parties thattransact via the marketplace 12, may operate loyalty programs that aresupported by one or more loyalty/promotions applications 74. Forexample, a buyer may earn loyalty or promotions points for eachtransaction established and/or concluded with a particular seller, andbe offered a reward for which accumulated loyalty points can beredeemed.

Category Management System

FIG. 3 is a network diagram illustrating one elements of a categorysystem 100. The category system 100 is connected to the marketplaces 82and 88 via a network 80. Although the category system 100 and themarketplaces 82 and 88 are connected in a peer-to-peer arrangement,other network arrangements may be used.

The marketplaces 82 and 88 may provide different retail operations, suchas an auction site or a virtual retail store. In addition, themarketplaces 82 and 88 may be located at different geographical areas.In one exemplary embodiment, both the marketplaces 82 and 88 providesellers with a category listing application for the seller to list themerchandise.

Located within each marketplace 82 and 88 are category managers 84, 86,90 and 92. Category managers 84 and 90 maintain updates for category Aat site 82 and 88 respectively. Category manager 86 is dedicated tocategory B and category manager 92 is responsible for category C. Themaintenance of the categories may include merging one category withanother, deleting a category, adding a new category or renaming acategory. It will be appreciated by one ordinarily skilled in the artthat a category manager may maintain multiple categories instead of asingle category. In addition, a single category manager, such ascategory managers 84, 86, 90 or 92, may be responsible for multiplesites.

The category managers 84, 86, 90 and 92 provide the updated informationof the categories to the category system 100. The provision of theupdated information may be performed on a periodical or real-time basis.The information includes the types of update performed on the category,such as merge, add, delete or rename. In addition, information relatingto the mapping of an old category to a new category is provided to thecategory system 100. For example, when category A is merged withcategory B, the mapping of category A to category B is submitted to thecategory system 100.

The category system 100 includes a data manager 94 and twodatabases—category listing database 96 and category relationshipdatabase 98. The data manager 94 receives the updated information fromthe category managers 84, 86, 90 and 92 and updates the changes in thedatabases 96 and 98. Using the earlier example, when category A ismerged with category B, the data manager 94 updates the category listingdatabase 96 by removing category A from the category listing database96. In addition, the data manager 94 adds the mapping of category A tocategory B to the category relationship database 98.

In one exemplary embodiment, an identifier is used to uniquely representeach category. The category identifier may be assigned by the categorysystem 100 or the category managers 84, 86, 90, and 92. The categoryidentifier may be of any data type, such as alphanumeric or specialcharacters. When a user submits a description of the category or theproduct, the parser 95 of the category system 100 translates thedescription based on the category listing database 96 and assigns acategory identifier. The category system 100 uses the categoryidentifier to perform searches and mappings on the databases 96 and 98.

Though the exemplary embodiment of the category system 100 isillustrated as a centralized system, it is not limited to such. Forexample, a distributed system may be set up with a category system 100located at each marketplace 82 and 88. Alternatively, a centralizedcategory system 100 may be configured to record the source of theupdates. For example, the centralized category system 100 is able toidentify that category A is updated at site 82 but not site 88.Therefore, a seller listing an item under category A is automaticallyre-categorized at site 82 but not at site 88.

Interactive Flowchart

FIG. 4 is an interactive flow chart illustrating a method, according toan exemplary embodiment of the present invention, to automaticallycategorize a merchant listing (e.g., describing an item or serviceavailable for transaction) submitted by a seller 102.

Starting at block 104, the seller 102 prepares listing information,describing an item or service that the seller may be offering for sale(or other transaction type, such as lease or rental for example) In oneembodiment, the seller 102 includes information such as pricing, productdescription, payment mode and one or more images in the listinginformation. In addition, if the seller 102 is aware of the categorieslisted in the marketplace, the seller 102 may specify, within thelisting information, the category or the category identifier of theitem. Alternatively, the seller 102 may choose to let the marketplacecategorize the item automatically.

The seller 102 submits the listing information to the category system100 in the market place at block 106. At block 108, the category system100 parses the listing information as submitted by the seller 102. Inone embodiment, the seller 102 provides a category description for theitem. The category system 100 translates the category description intothe appropriate category identifier by performing a search on thecategory listing database 96 at block 120. Prior versions of thecategory listing database 96 may be used to locate the categoryidentifier if the category description provided has expired.

Similarly, if the seller 102 provides a product description, thecategory system 100 translates the product description into the categoryidentifier for listing at block 120.

In the event that the seller 102 has provided a category identifier, thecategory system 100 compares the category identifier with theidentifiers in the latest version of the category listing database 96 atblock 110. As the category listing database 96 contains the mostup-to-date category identifier, the comparison process determines if thecategory identifier submitted by the seller 102 has expired. Likewise,the category identifier generated at block 120 is subject toverification at block 110.

Once the category identifier has been identified as expired, thecategory system 100 verifies if the seller 102 has given the categorysystem 100 the authority to update the category identifier automaticallyat block 112. In one instance, the seller 102 may choose to be notifiedat block 118 and use other means to update the category identifier. Ifthe category system 100 is authorized to automatically update thecategory identifier, the category system 100 performs a search on thecategory relationship database 98. Previous versions of the categoryrelationship database 98 may be used. The category relationship database98 contains a mapping of “old” (or previous) categories to “new” orcurrent categories. If a match is found, the old category identifier ismapped onto a new category identifier at block 114. Following in themapping of the old category identifier to the new category identifier,the listing information may be updated to record an association betweenthe new category identifier and the listing. Specifically, in oneembodiment, the category identifier that was previously associated with,or included in, the listing is replaced by the new category identifieras identified at block 114. In another embodiment, the new categoryidentifier may be associated with the item as a “current” categoryidentifier, and the “old” category identifier may be retained as a“previous” category identifier for the item. The updated listinginformation is then stored within a database of the electronicmarketplace. The electronic marketplace then operates to publish thelisting information utilizing the new category information, so that thelisting may be locatable utilizing a current category hierarchy of theelectronic marketplace.

Returning to the flowchart shown in FIG. 4, in the event that no matchis found at block 114, the seller 102 will be notified of the error atblock 116.

Category Listing Database and Category Relationship Database

FIG. 5 is a block diagram representing the data information in thecategory listing database 96 and the category relationship database 98.In one exemplary embodiment, as represented by block 132, the electronicmarketplace has a listing of categories A, B, C and D on January 2004.The category listing database 96 contains categories A, B, C and D whilethe category relationship database 98 is empty.

At block 134, the electronic marketplace decides to merge category Awith category B. The category system 100 removes category A from thecategory listing database 96 while maintaining categories B, C and D.The category relationship database 98 records the mapping of category Ato category B. In one embodiment, when the seller 102 submits an item ofcategory A, the category system 100 searches the category listingdatabase 96 for category A. As category A is not located in the categorylisting database 96, the category system 100 performs another searchusing the category relationship database 98. The category relationshipdatabase 98 indicates that category A is now mapped to category B.Therefore, the item is automatically listed under category B instead ofcategory A.

In another exemplary embodiment, the electronic marketplace mergescategory B with category C at block 136. Similarly, the category system100 removes category B from the category listing database 96. Thecategory listing database 96 now contains categories C and D. Inaddition, the category relationship database 98 is updated to remove themapping of category A to category B, add mappings of category A tocategory C and category B to category C. When a seller 102 submits anitem of category A or category B, the category system 100 automaticallyreclassifies the item under category C.

At block 138, the electronic marketplace re-lists category A, which haspreviously been merged with category B. The category system 100 updatesthe category listing database 96 with category A and removes the mappingof category A to category C from the category relationship database 98.In the event that the seller 102 submits an item of category A forlisting, the category system 100 is able to automatically list the itemunder category A as category A can be located in the category listingdatabase 96.

In another exemplary embodiment, the electronic marketplace renamescategory A as category Z, as illustrated at block 140. The categorysystem 100 handles the process by first deleting category A from thecategory listing database 96 and adding category Z. Next, the categorysystem 100 adds the mapping of category A to category Z in the categoryrelationship database 98. The category system 100 automaticallyclassifies an item of category A under category Z.

System Architecture

FIG. 6 shows a diagrammatic representation of a machine in the exemplaryform of a computer system 300 within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed. In alternative embodiments, themachine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client machine in server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine may be a server computer,a client computer, a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The exemplary computer system 300 includes a processor 302 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) or both),a main memory 304 and a static memory 306, which communicate with eachother via a bus 308. The computer system 300 may further include a videodisplay unit 310 (e.g., a liquid crystal display (LCD) or a cathode raytube (CRT)). The computer system 300 also includes an alphanumeric inputdevice 312 (e.g., a keyboard), a cursor control device 314 (e.g., amouse), a disk drive unit 316, a signal generation device 318 (e.g., aspeaker) and a network interface device 320.

The disk drive unit 316 includes a machine-readable medium 322 on whichis stored one or more sets of instructions (e.g., software 324)embodying any one or more of the methodologies or functions describedherein. The software 324 may also reside, completely or at leastpartially, within the main memory 304 and/or within the processor 302during execution thereof by the computer system 300, the main memory 304and the processor 302 also constituting machine-readable media.

The software 324 may further be transmitted or received over a network326 via the network interface device 320.

While the machine-readable medium 322 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present invention. The term “machine-readablemedium” shall accordingly be taken to include, but not be limited to,solid-state memories, and optical and magnetic media.

Thus, a method and system to automatically categorize merchant items inan electronic marketplace have been described. Although the presentinvention has been described with reference to specific exemplaryembodiments, it will be evident that various modifications and changesmay be made to these embodiments without departing from the broaderspirit and scope of the invention. Accordingly, the specification anddrawings are to be regarded in an illustrative rather than a restrictivesense.

What is claimed is:
 1. A method of creating a taxonomy and automaticallycategorizing a merchant listing, the method comprising: receiving adescription for each of one or more goods or services from a seller, theone or more goods or services each to be categorized as separate ones ofthe merchant listing; parsing, using one or more processors, thedescription of each of the one or more goods or services received fromthe seller; creating the taxonomy including preparing the merchantlisting for use within the taxonomy, the merchant listing to allow theseller in an electronic marketplace to author listings for each of theone or more goods or services, the preparing of the merchant listingincluding determining a category identifier for the merchant listingincluding, based on the parsing, making a determination based on thedescription whether the seller provided a category description andwhether the seller provided a product description for each of the one ormore goods or services; based on a determination that the sellerprovided a category description, translating the category descriptioninto the category identifier; and based on a determination that theseller provided a product description, translating the productdescription into the category identifier; the determining of thecategory identifier further including performing a first search tocompare the category identifier with a plurality of category identifiersin a first database, and associating a first category identifier withthe merchant listing, the first category identifier to categorize eachof the one or more goods or services for transaction in the electronicmarketplace; and based on a determination that no match was found as aresult of the first performed search, making a determination as towhether the seller had previously authorized an updating of the categoryidentifier to a more recent version of the category identifier; andbased on a determination that the seller had not previously authorizedthe updating of the category identifier to the more recent version ofthe category identifier, transmitting a message to the seller requestingauthorization of updating of the category identifier to the more recentversion of the category identifier; based on an evaluation that at leastone condition in a list of conditions occurred, where the list ofconditions includes a determination that the seller had authorized theupdating of the category identifier to the more recent version of thecategory identifier and that the seller authorized the updating of thecategory identifier, performing a second search to compare the categoryidentifier with a plurality of category relationships in a categoryrelationship database, provide a second category identifier of themerchant listing in response to a match being found in the secondperformed search, and associate the second category identifier with themerchant listing, the second category identifier to categorize each ofthe one or more goods or services for transaction in the electronicmarketplace; and based on a determination that no match was found ineither the first search or the second search, transmitting a message tothe seller that no match was found.
 2. The method of claim 1, furtherincluding translating description information of the merchant listinginto the category identifier.
 3. The method of claim 2, wherein thedescription information is at least one of a category description and aproduct description.
 4. The method of claim 2, wherein the translatingof the description information of the merchant listing into the categoryidentifier includes locating the description information of the merchantlisting in at least one of a current version and a previous version ofthe first database.
 5. The method of claim 1, wherein the plurality ofcategory relationships contains a mapping of an expired categoryidentifier, representing an expired category, to a current categoryidentifier, representing a current category.
 6. The method of claim 5,wherein the first category identifier is the expired category identifierand the second category identifier is the current category identifier.7. The method of claim 1, further including updating the plurality ofcategory relationships in the-category relationship database.
 8. Themethod of claim 7, wherein the updating of the plurality of categoryrelationships includes merging the first category identifier with thesecond category identifier.
 9. The method of claim 8, wherein themerging the first category identifier with the second categoryidentifier includes: removing the first category identifier from thefirst database; and adding a mapping of the first category identifier tothe second category identifier in the category relationship database.10. The method of claim 9, wherein the updating of the plurality ofcategory relationships further includes merging the second categoryidentifier with a third category identifier.
 11. The method of claim 10,wherein the merging of the second category identifier with the thirdcategory identifier includes: removing the second category identifierfrom the first database; removing the mapping of the first categoryidentifier to the second category identifier in the categoryrelationship database; adding a mapping of the first category identifierto the third category identifier in the category relationship database;and adding a mapping of the second category identifier to the thirdcategory identifier in the category relationship database.
 12. Themethod of claim 7, wherein the updating of the plurality of categoryrelationships includes adding a third category identifier that had beenpreviously removed from the first database.
 13. The method of claim 12,wherein the adding the third category identifier includes: adding thethird category identifier in the first database; and removing a mappingof the third category identifier in the category relationship database.14. The method of claim 7, wherein the updating the plurality ofcategory relationships includes renaming the first category identifieras a third category identifier.
 15. The method of claim 14, wherein therenaming the first category identifier as the third category identifierincludes: deleting the first category identifier in the first database;adding the third category identifier in the first database; replacingthe first category identifier with the third category identifier in thecategory relationship database; and adding a mapping of the firstcategory identifier to the third category identifier in the categoryrelationship database.
 16. A computer system for creating a taxonomy andautomatically categorizing a merchant listing, the system comprising: ataxonomy creation applications engine having a processor, the taxonomycreation applications engine to allow a seller in an electronicmarketplace to create a taxonomy and author listings for one or moregoods or services within the taxonomy, and receive a description foreach of the one or more goods or services from the seller, the one ormore goods or services each to be categorized as separate ones of themerchant listing; and storage media coupled to the processor, thestorage media including: means for parsing the description of each ofthe one or more goods or services received from the seller; means fordetermining a category identifier for the merchant listing including,based on the parsing, making a determination based on the descriptionwhether the seller provided a category description and whether theseller provided a product description for each of the one or more goodsor services; based on a determination that the seller provided acategory description, translating the category description into thecategory identifier; and based on a determination that the sellerprovided a product description, translating the product description intothe category identifier; the means for determining a category identifierfurther including means for performing a first search to compare thefirst category identifier with a plurality of category identifiers in afirst database; and means for associating a first category identifierwith the merchant listing, the first category identifier to categorizeeach of the one or more goods or services for transaction in theelectronic marketplace; and based on a determination that no match wasfound as a result of the first performed search, the means fordetermining a category identifier further for determining whether theseller had previously authorized an updating of the category identifierto a more recent version of the category identifier; and based on adetermination that the seller had not previously authorized the updatingof the category identifier to the more recent version of the categoryidentifier, means for transmitting a message to the seller requestingauthorization of updating of the category identifier to the more recentversion of the category identifier; based on an evaluation that at leastone condition in a list of conditions occurred, where the list ofconditions includes the determination that the seller had authorized anupdating of the category identifier to the more recent version of acategory identifier and that the seller authorized an updating of thecategory identifier, means for performing a second search to compare thecategory identifier with a plurality of category relationships in acategory relationship database; means for providing a second categoryidentifier of the merchant listing in response to a match being found inthe second performed search; and means for associating the secondcategory identifier with the merchant listing, the second categoryidentifier to categorize each of the one or more goods or services fortransaction in the electronic marketplace; and based on a determinationthat no match was found in either the first search or the second search,means for transmitting a message to the seller that no match was found.17. The system of claim 16, further including means for translatingdescription information of merchant listing into the categoryidentifier.
 18. The method of claim 17, wherein the descriptioninformation is at least one of a category description and a productdescription.
 19. The system of claim 17, wherein the means fortranslating the description information of the merchant listing into thecategory identifier includes locating the description information of themerchant listing in at least one of a current version and a previousversion of the first database.
 20. The system of claim 16, wherein theplurality of category relationships contains a mapping of an expiredcategory identifier, representing an expired category, to a currentcategory identifier, representing a current category.
 21. The system ofclaim 20, wherein the first category identifier is the expired categoryidentifier and the second category identifier is the current categoryidentifier.
 22. The system of claim 16, further including means forupdating of the plurality of category relationships in the categoryrelationship database.
 23. The system of claim 22, wherein the means forupdating of the plurality of category relationships includes means formerging the first category identifier with the second categoryidentifier.
 24. The system of claim 23, wherein the means for mergingthe first category identifier with the second category identifierincludes: means for removing the first category identifier from thefirst database; and means for adding a mapping of the first categoryidentifier to the second category identifier in the categoryrelationship database.
 25. The system of claim 24, wherein the means forupdating of the plurality of category relationships further includesmeans for merging the second category identifier with a third categoryidentifier.
 26. The system of claim 25, wherein the means for merging ofthe second category identifier with the third category identifierincludes: means for removing the second category identifier from thefirst database; means for removing the mapping of the first categoryidentifier to the second category identifier in the categoryrelationship database; means for adding a mapping of the first categoryidentifier to the third category identifier in the category relationshipdatabase; and means for adding a mapping of the second categoryidentifier to the third category identifier in the category relationshipdatabase.
 27. The system of claim 22, wherein the means for updating ofthe plurality of category relationships includes means for adding athird category identifier that had been previously removed from thefirst database.
 28. The system of claim 27, wherein the means for addingthe third category identifier includes: means for adding the thirdcategory identifier in the first database; and means for removing amapping of the third category identifier in the category relationshipdatabase.
 29. The system of claim 22, wherein the means for updating ofthe plurality of category relationships includes means for renaming thefirst category identifier as a third category identifier.
 30. The systemof claim 29, wherein the means for renaming the first categoryidentifier as the third category identifier includes: means for deletingthe first category identifier in the first database; means for addingthe third category identifier in the first database; means for replacingthe first category identifier with the third category identifier in thecategory relationship database; and means for adding a mapping of thefirst category identifier to the third category identifier in thecategory relationship database.
 31. A computer system to create ataxonomy and automatically categorize a merchant listing, the computersystem comprising: a taxonomy creation applications engine having aprocessor, the taxonomy creation applications engine to allow a sellerin an electronic marketplace to create a taxonomy and author listingsfor one or more goods or services within the taxonomy, and receive adescription for each of the one or more goods or services from theseller, the one or more goods or services each to be categorized asseparate ones of the merchant listing; a parser to parse the descriptionof each of the one or more goods or services received from the seller;and storage media coupled to the processor, the storage media including:a database application to determine a category identifier for themerchant listing including, based on the parsing of the description andto make a determination based on the description whether the sellerprovided a category description and whether the seller provided aproduct description for each of the one or more goods or services; basedon a determination that the seller provided a category description,translating the category description into the category identifier; andbased on a determination that the seller provided a product description,translating the product description into the category identifier; thedatabase application further to perform a first search by locating afirst category identifier within a first database, and associate a firstcategory identifier with the merchant listing, the first categoryidentifier to categorize each of the one or more goods or services fortransaction in the electronic marketplace; and based on a determinationthat no match was found as a result of the first performed search,further to make a determination as to whether the seller had previouslyauthorized an updating of the category identifier to a more recentversion of a category identifier; and based on a determination that theseller had not previously authorized the updating of the categoryidentifier to the more recent version of the category identifier, totransmit a message to the seller requesting authorization of updating ofthe category identifier to the more recent version of the categoryidentifier; based on an evaluation that at least one condition in a listof conditions occurred, where the list of conditions includes thedetermination that the seller had authorized an updating of the categoryidentifier to the more recent version of a category identifier and thatthe seller authorized an updating of the category identifier, databaseapplication further to perform a second search by locating the categoryidentifier with a category relationship database, provide a secondcategory identifier of the merchant listing in response to a match beingfound in the second performed search, and associate a second categoryidentifier with the merchant listing, the second category identifier tocategorize each of the one or more goods or services for transaction inthe electronic marketplace; and based on a determination that no matchwas found in either the first search or the second search, transmittinga message to the seller that no match was found.
 32. The system of claim31, wherein the parser is operable to translate description informationof the merchant listing into the category identifier.
 33. The system ofclaim 32, wherein the description information is at least one of acategory description and a product description.
 34. The system of claim32, wherein the parser is operable to locate the description informationof the merchant listing in at least one of a current version and aprevious version of the first database.
 35. The system of claim 31,wherein the first database includes a plurality of category identifiers.36. The system of claim 31, wherein the category relationship databaseincludes a plurality of category relationships representing a mapping ofan expired category identifier, representing an expired category, to acurrent category identifier, representing a current category.
 37. Thesystem of claim 36, wherein the first category identifier is the expiredcategory identifier and the second category identifier is the currentcategory identifier.
 38. The system of claim 31, wherein the databaseapplication is to update the first database and the categoryrelationship database.
 39. The system of claim 38, wherein the databaseapplication is to merge the first category identifier with the secondcategory identifier.
 40. The system of claim 39, wherein the databaseapplication is to remove the first category identifier from the firstdatabase and add a mapping of the first category identifier to thesecond category identifier in the category relationship database. 41.The system of claim 40, wherein the database application is to merge thesecond category identifier with a third category identifier.
 42. Thesystem of claim 41, wherein the database application is to remove thesecond category identifier from the first database, remove the mappingof the first category identifier to the second category identifier, adda mapping of the first category identifier to the third categoryidentifier and add a mapping of the second category identifier to thethird category identifier in the category relationship database.
 43. Thesystem of claim 38, wherein the database application is to add a thirdcategory identifier that had been previously removed from the firstdatabase.
 44. The system of claim 43, wherein the database applicationis to add the third category identifier in the first database and removea mapping of the third category identifier in the category relationshipdatabase.
 45. The system of claim 38, wherein the database applicationis to rename the first category identifier as a third categoryidentifier.
 46. The system of claim 45, wherein the database applicationis to delete the first category identifier in the first database, addthe third category identifier in the first database, replace the firstcategory identifier with the third category identifier in the categoryrelationship database and add a mapping of the first category identifierto the third category identifier in the category relationship database.47. A processor-readable storage medium not including any transitorycomponents and storing an instruction that, when executed by aprocessor, causes the processor to perform operations of creating ataxonomy and automatically categorizing a merchant listing, theoperations comprising: receiving a description for each of one or moregoods or services from a seller, the one or more goods or services eachto be categorized as separate ones of the merchant listing; parsing,using one or more processors, the description of each of the one or moregoods or services received from the seller; creating the taxonomyincluding preparing the merchant listing for use within the taxonomy,the merchant listing to allow the seller in an electronic marketplace toauthor listings for each of the one or more goods or services, thepreparing of the merchant listing including determining a categoryidentifier for the merchant listing including, based on the parsing,making a determination based on the description whether the sellerprovided a category description and whether the seller provided aproduct description for each of the one or more goods or services; basedon a determination that the seller provided a category description,translating the category description into the category identifier; andbased on a determination that the seller provided a product description,translating the product description into the category identifier; thedetermining of the category identifier further including performing afirst search to compare the category identifier with a plurality ofcategory identifiers in a first database, and associating a firstcategory identifier with the merchant listing, the first categoryidentifier to categorize each of the one or more goods or services fortransaction in the electronic marketplace; and based on a determinationthat no match was found as a result of the first performed search,making a determination as to whether the seller had previouslyauthorized an updating of the category identifier to a more recentversion of a category identifier; and based on a determination that theseller had not previously authorized the updating of the categoryidentifier to the more recent version of the category identifier,transmitting a message to the seller requesting authorization ofupdating of the category identifier to the more recent version of thecategory identifier; based on an evaluation that at least one conditionin a list of conditions occurred, where the list of conditions includesthe determination that the seller had authorized an updating of thecategory identifier to the more recent version of a category identifierand that the seller authorized an updating of the category identifier,performing a second search to compare the category identifier with aplurality of category relationships in a category relationship database,provide a second category identifier of the merchant listing in responseto a match being found in the second performed search, and associate thesecond category identifier with the merchant listing, the secondcategory identifier to categorize each of the one or more goods orservices for transaction in the electronic marketplace; and based on adetermination that no match was found in either the first search or thesecond search, transmitting a message to the seller that no match wasfound.
 48. The processor-readable storage medium of claim 47, furtherincluding translating description information of the merchant listinginto the category identifier.
 49. The processor-readable storage mediumof claim 48, wherein the description information is at least one of acategory description and a product description.
 50. Theprocessor-readable storage medium of claim 48, wherein the translatingof the description information of the merchant listing into the categoryidentifier includes locating the description information of the merchantlisting in at least one of a current version and a previous version ofthe first database.
 51. The processor-readable storage medium of claim47, wherein the plurality of category relationships contains a mappingof an expired category identifier, representing an expired category, toa current category identifier, representing a current category.
 52. Theprocessor-readable storage medium of claim 51, wherein the firstcategory identifier is the expired category identifier and the secondcategory identifier is the current category identifier.
 53. Theprocessor-readable storage medium of claim 47, further including anupdating of the plurality of category relationships in the categoryrelationship database.
 54. The processor-readable storage medium ofclaim 53, wherein the updating of the plurality of categoryrelationships includes merging the first category identifier with thesecond category identifier.
 55. The processor-readable storage medium ofclaim 54, wherein the merging the first category identifier with thesecond category identifier includes: removing the first categoryidentifier from the first database; and adding a mapping of the firstcategory identifier to the second category identifier in the categoryrelationship database.
 56. The processor-readable storage medium ofclaim 55, wherein the updating the plurality of category relationshipsfurther includes merging the second category identifier with a thirdcategory identifier.
 57. The processor-readable storage medium of claim56, wherein the merging the second category identifier with the thirdcategory identifier includes: removing the second category identifierfrom the first database; removing the mapping of the first categoryidentifier to the second category identifier in the categoryrelationship database; adding a mapping of the first category identifierto the third category identifier in the category relationship database;and adding a mapping of the second category identifier to the thirdcategory identifier in the category relationship database.
 58. Theprocessor-readable storage medium of claim 53, wherein the updating ofthe plurality of category relationships includes adding a third categoryidentifier that had been previously removed from the first database. 59.The processor-readable storage medium of claim 58, wherein the addingthe third category identifier includes: adding the third categoryidentifier in the first database; and removing a mapping of the thirdcategory identifier in the category relationship database.
 60. Theprocessor-readable storage medium of claim 53, wherein the updating ofthe plurality of category relationships includes renaming the firstcategory identifier as a third category identifier.
 61. Theprocessor-readable storage medium of claim 60, wherein the renaming ofthe first category identifier as the third category identifier includes:deleting the first category identifier in the first database; adding thethird category identifier in the first database; replacing the firstcategory identifier with the third category identifier in the categoryrelationship database; and adding a mapping of the first categoryidentifier to the third category identifier in the category relationshipdatabase.